-
Notifications
You must be signed in to change notification settings - Fork 27
Workaround juju 21047 #1154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workaround juju 21047 #1154
Conversation
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (67.44%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## 16/edge #1154 +/- ##
========================================
Coverage 67.44% 67.44%
========================================
Files 18 18
Lines 3947 3947
Branches 564 564
========================================
Hits 2662 2662
Misses 1112 1112
Partials 173 173 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Can you please create backlog Jira/GH to revert this once Juju is fixed.
Otherwise we will forget. Tnx!
|
Issue
juju/juju#21047 causes failures in the redeployment tests and also in one of the GCP backup tests (which rereploys the charm in the same model with the same name).
Solution
Mark redeployment tests as unstable and change the GCP backup test.
Also, update the redis-k8s channel and base to the ones that are currently working.
Checklist